Back إدماج مستمر Arabic Непрекъсната интеграция Bulgarian Integració contínua Catalan Průběžná integrace Czech Kontinuierliche Integration German Integración continua Spanish Pidev integratsioon Estonian Integrazio etengabe Basque یکپارچهسازی مداوم Persian Jatkuva integraatio Finnish
 | This article includes a list of general references, but it lacks sufficient corresponding inline citations. (July 2016) |
| Part of a series on |
| Software development |
|---|
Continuous integration (CI) is the practice of frequently building and testing a software system during its development. It is intended to ensure that code written by programmers is always buildable, runnable and passes automated testing. Developers merge to an integration branch and an automated system builds and tests.[1] Often, the automated process runs on each commit or runs on a schedule such as once a day.
Grady Booch first proposed the term CI in 1991,[2] although he did not advocate integrating multiple times a day, but later, CI came to include that aspect.[3]
- ^ Cite error: The named reference
martinfowlerwas invoked but never defined (see the help page). - ^ Booch, Grady (1991). Object Oriented Design: With Applications. Benjamin Cummings. p. 209. ISBN 9780805300918. Retrieved 18 August 2014.
- ^ Beck, K. (1999). "Embracing change with extreme programming". Computer. 32 (10): 70–77. doi:10.1109/2.796139. ISSN 0018-9162.
© MMXXIII Rich X Search. We shall prevail. All rights reserved. Rich X Search